Apparatus and methods for managing service delivery telemetry

ABSTRACT

Apparatus and methods for managing service delivery quality levels and telemetry. In one embodiment, an entity (such as a Session Resource Manager or SRM) receives network layout data from the network. The SRM uses the layout data to generate a mapping of the network. The SRM also receives performance data related to the interconnections of the network. The performance data is then applied to the mapping such that, in one variant, an visual overlay showing network flow and/or performance analytics is created. Based on this mapping showing layout and corresponding performance, the SRM generates rules for delivery of services. The rules may detail preferred routes and service level information. The rules are the distributed to nodes along the delivery route and delivery is executed in compliance with the rules.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND 1. Technological Field

The present disclosure relates generally to the field of content and/ordata delivery over a network. More particularly, the present disclosureis related, in one exemplary aspect, to apparatus and methods formanagement of quality of service for managed service provision via anexternal network.

2. Description of Related Technology

The proliferation of the Internet and increased connection technologiessuch as broadband has contributed to the development of differentavenues for content provision, such as for example Internet Protocol(IP) delivery. Accordingly, these new avenues have allowed for deliveryof content to previously unavailable customer bases over, e.g.,externally managed networks (EMNs).

These externally managed networks include, without limitation, networksof competing service providers, municipalities, enterprises, andnon-profit groups such as universities. In the absence of theaforementioned avenues, provision of information services (such astelevision or other content services) or telecommunications services tothese externally managed networks is generally limited to a single ownerof the underlying physical data lines. Alternatively, these services maybe provided wholesale to the externally managed network with limitedservice support options for network administrators.

However, the provision of services over EMNs presents challenges forservice providers. For example, a service provider (e.g. multiplesystems operator or “MSO”) providing IP television (IPTV) service to auniversity is simultaneously charged with providing reliable IPTVservice, while having only limited (or no) control of the “last mile” ofthe delivery network. Thus, the IPTV service provider may be heldresponsible for delivery failures or periods of limited service withoutoptions for mitigation available because of this limited control. Forexample, the service provider may be improperly held responsible for abuffer underrun error resulting in a loss of IPTV playback at userdevice. In this case, the responsible party may be the administrator ofthe network infrastructure of the EMN charged with last mile delivery.As such, the service provider may receive a service complaint and beunable to restore operation of the network infrastructure (or evenproperly diagnose the issue).

The aforementioned problem is compounded by the fact that services suchas high-definition (HD) IPTV have comparatively daunting quality ofservice requirements. Further, denying service options to externallymanaged network operators based on their network's current capabilities,or forcing upgrades to such capabilities as a predicate to service, mayunduly limit service opportunities.

Hence, flexible management tools for maintaining quality of service onexternal networks are one salient need presented by the foregoingsituation. Ideally, such tools should allow for implementation ofservices with varying quality of service requirements and integrationwith a wide variety of network architectures.

SUMMARY

The present invention addresses the foregoing needs by disclosing, interalia, apparatus and methods for management of quality of service formanaged service provision.

In a first aspect of the disclosure, a method of managing service levelsin a network is disclosed. In one embodiment, the method includes: (i)receiving networking data from a group of network nodes, (ii) using atleast the networking data, determining the layout of the network, (iii)receiving performance information and/or connection type information forat least one node of the group of nodes, and (iv) determining one ormore delivery rules for the at least one node of the group of nodes.

In one variant, the method further includes causing content delivery tothe at least one node of the plurality of nodes to comply with the oneor more delivery rules.

In a second aspect of the disclosure, a method of content delivery isdisclosed. In one embodiment, the method includes: (i) receiving dataassociated with a mapping of a network, (ii) identifying a route forcontent delivery to a network device using the received data, (iii)receiving a connection profile associated with an infrastructure elementand/or the network device, (iv) using the at least one connectionprofile and the route to identify a quality level for the contentdelivery, and (v) initiating transmission of the content in accordancewith the determined quality level.

In a third aspect of the disclosure, a service management apparatus isdisclosed. In one embodiment, the apparatus includes a network interfaceand processing logic.

In a variant, the network interface is configured to receive networklayout data from a plurality of nodes of an externally managed network,and transmit one or more rules related to a service delivery level forat least one of the plurality of nodes. Further, the processing logic isconfigured to run one or more processes thereon. In one implementation,the one or more processes include a plurality of instructions configuredto, when executed, generate a network map of the externally managednetwork using the received network layout data, and based at least inpart on the generated network map, determine the one or more rulesrelated to the service delivery level for the at least one of theplurality of nodes.

In a fourth aspect of the disclosure, a non-transitory computer-readableapparatus configured to store one or more computer programs thereon isdisclosed. In one embodiment, the one or more computer programs includea plurality of instructions configured to, when executed: collect rawnetworking data from one or more network nodes, analyze the collectedraw networking data to determine a network layout, analyze the collectedraw networking data to associate one or more performance levels with atleast one of the one or more network nodes, assign at least one deliveryrule to the at least one of the one or more network nodes, and send theat least one delivery rule to a network entity associated with deliveryof a service to the at least one node.

In a fifth aspect of the disclosure, a service delivery apparatus isdisclosed. In one embodiment, the service delivery apparatus includesprocessing logic configured to, inter alia, receive and enforce servicedelivery rules.

In a sixth aspect of the disclosure, computerized logic is disclosed. Inone embodiment, the logic is configured to implement at least oneprocess configured to, inter alia, execute service delivery inaccordance with one or more rules received from a management entity.

These and other aspects become apparent when considered in light of thedisclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating an exemplary hybridfiber network configuration useful with various aspects of the presentdisclosure.

FIG. 1a is a functional block diagram illustrating one exemplary networkheadend configuration.

FIG. 1b is a functional block diagram illustrating one exemplary localservice node configuration useful with various aspects of the presentdisclosure.

FIG. 1c is a functional block diagram illustrating one exemplarybroadcast switched architecture (BSA) network.

FIG. 1d is a functional block diagram illustrating one exemplarypacketized content delivery network architecture useful with variousaspects of the present disclosure.

FIG. 2 is a functional block diagram illustrating an exemplaryembodiment of a network architecture according to the presentdisclosure.

FIG. 2A is a functional block diagram illustrating an exemplary visualrepresentation of a network mapping.

FIG. 3 is a logical flow diagram illustrating an exemplary embodiment ofa method for service delivery management.

FIG. 4 is a logical flow diagram illustrating an exemplary embodiment ofa method for service delivery in accordance with the present disclosure.

FIG. 5 is a functional block diagram illustrating an exemplaryembodiment of management apparatus according to the present disclosure.

FIG. 6 is a functional block diagram depicting an exemplaryvisualization of an exemplary network layout.

All Figures © Copyright 2012-2013 Time Warner Cable, Inc. All rightsreserved.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “application” refers generally to a unit ofexecutable software that implements a certain functionality or theme.The themes of applications vary broadly across any number of disciplinesand functions (such as on-demand content management, e-commercetransactions, brokerage transactions, home entertainment, calculatoretc.), and one application may have more than one theme. The unit ofexecutable software generally runs in a predetermined environment; forexample, the unit could comprise a downloadable Java Xlet™ that runswithin the JavaTV™ environment.

As used herein, the terms “client device” and “end user device” include,but are not limited to, set top boxes (e.g., DSTBs), personal computers(PCs), and minicomputers, whether desktop, laptop, or otherwise, andmobile devices such as handheld computers, tablets, “phablets”, PDAs,personal media devices (PMDs), and smartphones.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.), Binary Runtime Environment (e.g., BREW), andthe like.

The term “Customer Premises Equipment (CPE)” refers to any type ofelectronic equipment located within a customer's or user's premises andconnected to a network, such as set-top boxes (e.g., DSTBs or IPTVdevices), televisions, cable modems (CMs), embedded multimedia terminaladapters (eMTAs), whether stand-alone or integrated with other devices,Digital Video Recorders (DVR), gateway storage devices (Furnace), andITV Personal Computers.

As used herein, the term “display” means any type of device adapted todisplay information, including without limitation CRTs, LCDs, TFTs,plasma displays, LEDs, OLEDs, incandescent and fluorescent devices.Display devices may also include less dynamic devices such as, forexample, printers, e-ink devices, and the like.

As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet.

As used herein, the term “memory” or “storage” includes any type ofintegrated circuit or other storage device adapted for storing digitaldata including, without limitation, ROM. PROM, EEPROM, DRAM, SDRAM,DDR/2 SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR),and PSRAM.

As used herein, the terms “microprocessor” and “digital processor” aremeant generally to include all types of digital processing devicesincluding, without limitation, digital signal processors (DSPs), reducedinstruction set computers (RISC), general-purpose (CISC) processors,microprocessors, gate arrays (e.g., FPGAs), PLDs, reconfigurable computefabrics (RCFs), array processors, and application-specific integratedcircuits (ASICs). Such digital processors may be contained on a singleunitary IC die, or distributed across multiple components.

As used herein, the terms “MSO” or “multiple systems operator” referwithout limitation to a cable, satellite, or terrestrial networkprovider having infrastructure required to deliver services includingprogramming and data over those mediums.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (HFC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications or networking protocols(e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP,3GPP2, LTE/LTE-A, WAP, SIP, UDP, FTP, RTP/RTCP, H.323, etc.).

As used herein, the term “network interface” refers to any signal ordata interface with a component or network including, withoutlimitation, those of the Firewire (e.g., FW400, FW800, etc.), USB (e.g.,USB2), Ethernet (e.g., 10/100, 10/100/1000 (Gigabit Ethernet), 10-Gig-E,etc.), MoCA, Serial ATA (e.g., SATA, e-SATA, SATAII), Ultra-ATA/DMA,Coaxsys (e.g., TVnet™), radio frequency tuner (e.g., in-band or OOB,cable modem, etc.), Wi-Fi (802.11a,b,g,n), Wi-MAX (802.16), PAN(802.15), cellular (e.g., LTE/LTE-A, 3GPP, 3GPP2, UMTS), or IrDAfamilies.

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “user interface” refers to, without limitation,any visual, graphical, tactile, audible, sensory, or other means ofproviding information to and/or receiving information from a user orother entity.

As used herein, the term “Wi-Fi” refers to, without limitation, any ofthe variants of IEEE-Std. 802.11 or related standards including 802.11a/b/g/n/v.

As used herein, the term “wireless” means any wireless signal, data,communication, or other interface including without limitation Wi-Fi,Bluetooth, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A,WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20, NFC(e.g., ISO 14443A/B), narrowband/FDMA, OFDM, PCS/DCS, LTE/LTE-A/TD-LTE,analog cellular, Zigbee, CDPD, satellite systems, millimeter wave ormicrowave systems, acoustic, and infrared (i.e., IrDA).

Overview

In one salient aspect, the present disclosure provides apparatus andmethods for optimizing delivery telemetry via network mapping. In oneembodiment, a session resource manager (SRM) or other logical entitycollects information relating to network layout, and maps networkperformance to this layout. The SRM system uses knowledge of existingnetwork topology to optimize telemetry preferences for devices in thenetwork so as to monitor, adapt, and deliver stable, quality services toend users.

In an exemplary implementation, the SRM receives network layout datafrom the managed network. The SRM uses the layout data to generate amapping of the network. The SRM also receives performance data relatedto the interconnects of the network. The performance data is thenapplied to the mapping such that an overlay showing network flow iscreated. Based on this mapping showing layout and correspondingperformance, the SRM generates rules for delivery of services. The rulesmay for example detail preferred routes and service level information.The rules are the distributed to some or all of the nodes along thedelivery route, and delivery is executed in compliance with the rules.

In addition, the SRM affords administrators a centralized location forenforcement of network policies. For example, the administrator may setguidelines for service delivery level by altering settings of the SRMrather than updating policies on every affected node. The policies arethen enforced by the SRM regardless of whether such guidelines arewarranted by network performance and layout.

Further, the SRM may be used to diagnose problems in the mapped network.For example, if an increased number of failures are noticed for aportion of the network, the SRM may alert an administrator of theproblem area. Further, the mapping generated by the SRM may be used tocreate a visualization of the network, from which performance may bemonitored. The visualization allows for an administrator to quicklypinpoint areas of the network with service issues and assists indiagnosis. In one implementation, a ‘netmask’ view may be applied to thevisualization such that the operator may focus on a specific region orportion of the network.

Detailed Description of Exemplary Embodiments

Exemplary embodiments of the apparatus and methods of the presentinvention are now described in detail. While these exemplary embodimentsare described in the context of a managed hybrid fiber coax (HFC) cablesystem architecture having a multiple systems operator, digitalnetworking capability, and plurality of client devices/CPE, the generalprinciples and advantages of the invention may be extended to othertypes of networks and architectures, whether broadband, narrowband,wired or wireless, terrestrial or satellite, managed or unmanaged (orcombinations thereof), or otherwise, the following therefore beingmerely exemplary in nature.

It will also be appreciated that while described generally in thecontext of institutional service provision (e.g. academic, commercial,government, non-profit, etc.), the present invention may be readilyadapted to other types of environments (e.g., home networks, etc.) aswell. Myriad other applications are possible.

Further, although described in the context of service provision over anexternally managed network, the architectures and techniques describedherein may be readily applied to internal network management. Theexternal managed network embodiments presented are merely used todemonstrate the flexibility and general applicability of the principlesdescribed herein (e.g. may be implemented with or without fulladministrator control of a network) and should not be considered in anyway limiting.

In addition, while the disclosure refers at numerous points to one ormore interne protocol television (IPTV) embodiments, the principles ofthe disclosure are contemplated in other applications, such as videoservices (e.g., network DVR, second screen apps, cloud based digitalnavigators, OnDemand or over-the-top (OTT) content (e.g., Netflix®,Hulu®, virtual MSO services, etc.)), visual communications (i.e.,Skype®, Facetime®, etc), or cloud computing/storage/streaming services.All such embodiments are considered disclosed herein.

Also, while certain aspects are described primarily in the context ofthe well-known Internet Protocol (described in, inter cilia, RFC 791 and2460), it will be appreciated that the present invention may utilizeother types of protocols (and in fact bearer networks to include otherinternets and intranets) to implement the described functionality.

Bearer Network—

FIG. 1 illustrates a typical content delivery network configuration. Thevarious components of the network 100 include (i) one or more data andapplication origination points 102; (ii) one or more content sources103, (iii) one or more application distribution servers 104; (iv) one ormore VOD servers 105, and (v) customer premises equipment (CPE) 106. Thedistribution server(s) 104, VOD servers 105 and CPE(s) 106 are connectedvia a bearer (e.g., HFC) network 101. A simple architecture comprisingone of each of the aforementioned components 102, 104, 105, 106 is shownin FIG. 1 for simplicity, although it will be recognized that comparablearchitectures with multiple origination points, distribution servers,VOD servers, and/or CPE devices (as well as different networktopologies) may be utilized consistent with the disclosure. For example,the headend architecture of FIG. 1a (described in greater detail below),or others, may be used.

The data/application origination point 102 comprises any medium thatallows data and/or applications (such as a VOD-based or “Watch TV”application) to be transferred to a distribution server 104. This caninclude for example a third party data source, application vendorwebsite, CD-ROM, external network interface, mass storage device (e.g.,RAID system), etc. Such transference may be automatic, initiated uponthe occurrence of one or more specified events (such as the receipt of arequest packet or ACK), performed manually, or accomplished in anynumber of other modes readily recognized by those of ordinary skill. Theapplication distribution server 104 comprises a computer system wheresuch applications can enter the network system. Distribution servers arewell known in the networking arts, and accordingly not described furtherherein.

The VOD server 105 comprises a computer system where on-demand contentcan be received from one or more of the aforementioned data sources 102and enter the network system. These servers may generate the contentlocally, or alternatively act as a gateway or intermediary from adistant source.

The CPE 106 includes any equipment in the “customers' premises” (orother locations, whether local or remote to the distribution server 104)that can be accessed by a distribution server 104.

Referring now to FIG. 1a , one exemplary embodiment of a headendarchitecture is described. As shown in FIG. 1a , the headendarchitecture 150 comprises typical headend components and servicesincluding billing module 152, subscriber management system (SMS) and CPEconfiguration management module 154, cable-modem termination system(CMTS) and OOB system 156, as well as LAN(s) 158, 160 placing thevarious components in data communication with one another. It will beappreciated that while a bar or bus LAN topology is illustrated, anynumber of other arrangements as previously referenced (e.g., ring, star,etc.) may be used consistent with the disclosure. It will also beappreciated that the headend configuration depicted in FIG. 1a ishigh-level, conceptual architecture, and that each MSO may have multipleheadends deployed using custom architectures.

The exemplary architecture 150 of FIG. 1a further includes amultiplexer-encrypter-modulator (MEM) 162 coupled to the HFC network 101adapted to process or condition content for transmission over thenetwork. The distribution servers 164 are coupled to the LAN 160, whichprovides access to the MEM 162 and network 101 via one or more fileservers 170. The VOD servers 105 are coupled to the LAN 160 as well,although other architectures may be employed (such as for example wherethe VOD servers are associated with a core switching device such as an802.3z Gigabit Ethernet device). As previously described, information iscarried across multiple channels. Thus, the headend must be adapted toacquire the information for the carried channels from various sources.Typically, the channels being delivered from the headend 150 to the CPE106 (“downstream”) are multiplexed together in the headend, aspreviously described and sent to neighborhood hubs (FIG. 1b ) via avariety of interposed network components.

It will also be recognized, however, that the multiplexing operation(s)need not necessarily occur at the headend 150 (e.g., in theaforementioned MEM 162). For example, in one variant, at least a portionof the multiplexing is conducted at a BSA switching node or hub (seediscussion of FIG. 1c provided subsequently herein). As yet anotheralternative, a multi-location or multi-stage approach can be used, suchas that described in U.S. Pat. No. 7,602,820, entitled “APPARATUS ANDMETHODS FOR MULTI-STAGE MULTIPLEXING IN A NETWORK” incorporated hereinby reference in its entirety, which discloses inter alia improvedmultiplexing apparatus and methods that allow such systems todynamically compensate for content (e.g., advertisements, promotions, orother programs) that is inserted at a downstream network node such as alocal hub, as well as “feed-back” and “feed forward” mechanisms fortransferring information between multiplexing stages.

Content (e.g., audio, video, data, files, etc.) is provided in eachdownstream (in-band) channel associated with the relevant service group.To communicate with the headend or intermediary node (e.g., hub server),the CPE 106 may use the out-of-band (OOB) or DOCSIS channels andassociated protocols. The OCAP 1.0, 2.0, 3.0 (and subsequent)specification provides for exemplary networking protocols bothdownstream and upstream, although the present disclosure is in no waylimited to these approaches.

“Switched” Networks—

FIG. 1c illustrates an exemplary “switched” network architecture. Whilea so-called “broadcast switched architecture” or BSA network isillustrated in this exemplary network architecture embodiment, it willbe recognized that the present disclosure is in no way limited to sucharchitectures.

Switching architectures allow improved efficiency of bandwidth use forordinary digital broadcast programs. Ideally, the subscriber is unawareof any difference between programs delivered using a switched networkand ordinary streaming broadcast delivery.

FIG. 1c shows the implementation details of one exemplary embodiment ofthis broadcast switched network architecture. Specifically, the headend150 contains switched broadcast control and media path functions 190,192; these element cooperating to control and feed, respectively,downstream or edge switching devices 194 at the hub site which are usedto selectively switch broadcast streams to various service groups. A BSAserver 196 is also disposed at the hub site, and implements functionsrelated to switching and bandwidth conservation (in conjunction with amanagement entity 198 disposed at the headend). An optical transportring 197 is utilized to distribute the dense wave-division multiplexed(DWDM) optical signals to each hub in an efficient fashion.

Co-owned and co-pending U.S. Patent Application Publication No.2003/0056217 filed Sep. 20, 2001 and entitled “TECHNIQUE FOR EFFECTIVELYPROVIDING PROGRAM MATERIAL IN A CABLE TELEVISION SYSTEM”, incorporatedherein by reference in its entirety, describes one exemplary broadcastswitched digital architecture, although it will be recognized by thoseof ordinary skill that other approaches and architectures may besubstituted.

In addition to “broadcast” content (e.g., video programming), thesystems of FIGS. 1a and 1c (and 1 d discussed below) also deliverInternet data services using the Internet protocol (IP), although otherprotocols and transport mechanisms of the type well known in the digitalcommunication art may be substituted. One exemplary delivery paradigmcomprises delivering MPEG-based video content, with the videotransported to user PCs (or IP-based STBs) over the aforementionedDOCSIS channels comprising MPEG (or other video codec such as H.264 orAVC) over IP over MPEG. That is, the higher layer MPEG- or other encodedcontent is encapsulated using an IP protocol, which then utilizes anMPEG packetization of the type well known in the art for delivery overthe RF channels. In this fashion, a parallel delivery mode to the normalbroadcast delivery exists; i.e., delivery of video content both overtraditional downstream QAMs to the tuner of the user's STB or otherreceiver device for viewing on the television, and also as packetized IPdata over the DOCSIS QAMs to the user's PC or other IP-enabled devicevia the user's cable modem. Delivery in such packetized modes may beunicast, multicast, or broadcast.

Referring again to FIG. 1c , the IP packets associated with Internetservices are received by edge switch 194, and in one embodimentforwarded to the cable modem termination system (CMTS) 199. The CMTSexamines the packets, and forwards packets intended for the localnetwork to the edge switch 194. Other packets are discarded or routed toanother component.

The edge switch 194 forwards the packets receive from the CMTS 199 tothe QAM modulator 189, which transmits the packets on one or morephysical (QAM-modulated RF) channels to the CPE. The IP packets aretypically transmitted on RF channels (e.g., DOCSIS QAMs) that aredifferent that the RF channels used for the broadcast video and audioprogramming, although this is not a requirement. The CPE 106 are eachconfigured to monitor the particular assigned RF channel (such as via aport or socket ID/address, or other such mechanism) for IP packetsintended for the subscriber premises/address that they serve.

“Packetized” Networks—

While the foregoing network architectures described herein can (and infact do) carry packetized content (e.g., IP over MPEG for high-speeddata or Internet TV, MPEG2 packet content over QAM for MPTS, etc.), theyare often not optimized for such delivery. Hence, in accordance withanother embodiment of the disclosure, a “packet optimized” deliverynetwork is used for carriage of the packet content (e.g., IPTV content).FIG. 1d illustrates one exemplary implementation of such a network, inthe context of a 3GPP IMS (IP Multimedia Subsystem) network with commoncontrol plane and service delivery platform (SDP), as described inco-pending U.S. Provisional Patent Application Ser. No. 61/256,903 filedOct. 30, 2009 and entitled “METHODS AND APPARATUS FOR PACKETIZED CONTENTDELIVERY OVER A CONTENT DELIVERY NETWORK”, which is now published asU.S. Patent Application Publication No. 2011/0103374 of the same titlefiled on Apr. 21, 2010, each of which is incorporated herein byreference in its entirety. Such a network provides, inter alia,significant enhancements in terms of common control of differentservices, implementation and management of content delivery sessionsaccording to unicast or multicast models, etc.; however, it isappreciated that the various features of the present disclosure are inno way limited to this or any of the other foregoing architectures.

Session Resource Management Network Architecture—

FIG. 2 is a block diagram illustrating an exemplary network architecture200 for enabling managed service provision (including e.g., managementof quality of service requirements) over an externally managed network,configured in accordance with one embodiment of the disclosure. Theexemplary illustrated network entities and apparatus are configured tooperate within one or more of various the above-described bearernetworks of FIGS. 1-1 d, although others may readily be used. Thenetwork may be based on wireless and/or wireline networking technologies(e.g. Wi-Fi family 802.11, WiMAX 802.16, wired Ethernet standards(802.3), or optical standards, etc.). It will be appreciated thatbridges may be used to create a hybrid network environment usingmultiple ones of such technologies (e.g. wireless/wired Ethernethybrid).

As shown, the network architecture 200 generally includes an sessionresource manager (SRM) entity 202 in communication with a plurality ofnetwork nodes 206, one or more parent nodes 208, and a service resource(e.g. an IPTV server, etc.). The nodes and the parent nodes are disposedwithin the architecture of the externally managed network (EMN) 212, andthe service resource is included within the service provider network(SPN) 214. The SRM itself may be included within the EMN or SPN ordistributed across both networks. The SRM may be implemented in anynumber of different forms, including without limitation as a “virtual”entity or process running on extant hardware within the architecture, oras a separate substantially stand-alone device (e.g., server or blade).

It will be appreciated that the parent and child nodes may be several“generations” deep. Although not shown, nodes may be “grandparent”,“great grandparent” nodes, and so on. Further, in variousimplementations, one or more end user nodes may have a directout-of-network connection to the service resource (i.e., lacking aparent node).

The service resource 210 provides content to the parent nodes 208 of theEMN. The parent nodes then forward the content to the nodes 206, whichmay comprise end user local networks of one or more devices. Dependingon the implementation, the parent nodes and nodes may optionally engagein peering 216 to receive the content.

The SRM 202 gathers information on the connection characteristics of thevarious nodes and parent nodes of the EMN 212, and develops a “mapping”of the EMN. As used in this context, the term “mapping” refers withoutlimitation to any structural, relational, graphical representation ofnetwork topology. For example, a mapping may include a listing of nodesand the various interconnects between the nodes. The mapping may bestatic or dynamic. For example, an SRM capable of dynamic mapping mayhave access to dynamic host configuration protocol (DHCP) information,and may be kept apprised of devices and infrastructure elements as theyare added to the network.

The exemplary implementation of the mapping also includes connectionperformance. Initially, the performance information may comprise forinstance a “best guess” based on the connection mapping and performanceof nodes with similar routing to the service resource (e.g. those withsimilar parent nodes, nodes with similar authorized service levels, ornodes with similar numbers of available parallel route options).However, as the node develops its own “track record”, the performanceinformation may then be more clearly resolved such as by using the usagehistory.

In various implementations, the manager of the EMN mayalso/alternatively provide the SRM with mapping and/or performanceinformation on the nodes. This information may detail, for example,types of classes for the connectivity of the nodes on the network (e.g.identifying VIP nodes with higher bandwidth allocations, or throttlednodes associated with excessive use). In some cases, this informationmay be used in conjunction with the above-discussed estimates and usagehistory to calculate the connection performance.

With the mapped relationships and performance information, the exemplaryimplementation of the SRM generates a connection profile for each of thenodes and parent nodes. The connection profile in one embodimentdictates the delivery characteristics of the service from the SPN. Forexample, in an TPTV system. the connection profile may detail thedefault (and/or maximum) video quality that may be delivered to aparticular node. In some embodiments, the video quality may be steppedup from this default in optimal connection conditions (e.g. low trafficat a parent node), or stepped down in below-average conditions (e.g.service interruptions).

The connection profile may also include multiple entries, in variousimplementations. For example, in the case of peer-to-peer delivery 216,a node may have video quality options only present when content is edgepositioned.

The connection profile itself may be dynamic, allowing for optimizationof resource usage. Again, returning to the example of IPTV, rather thanenforcing a default video quality, the system may select a video qualitybased in part on current conditions, and in part on the profile.

In various implementations, the SRM may be used to diagnose problems inthe EMN. For example, if an increased number of failures or generalunder performance is detected for a group of peer nodes (i.e. those ofthe same parent). The SRM may infer that the corresponding parent may bemalfunctioning and may alert an administrator (e.g. by displaying analert or by sending an alert message to a terminal associated with theadministrator, etc.). Alternatively, such malfunctions orunderperformance may indicate improper connection profiles in the SRM'smapping. The SRM may then take appropriate action. For example, in anexemplary IPTV implementation, the SRM may reduce the video qualityuntil such malfunctions fall below a predetermined threshold.

The SRM system allows operators to leverage knowledge of existingnetwork topology, and strategically pre-assign optimal telemetryprofiles to devices at customer premises and/or along the network tomonitor, adapt, and deliver and ensure consistent quality of experienceto the end users without over-burdening the EMN.

It will be appreciated that the SRM mapping solution can be abstractedas e.g., a graph-based challenge, where an operator follows the depthfirst approach to traverse the network topology to all possible endnodes (e.g. devices at customer premises) and determine the bestpossible telemetry profile for those terminating devices. Then, theoperator may follow a breadth first approach to deterministically assignoptimal telemetry profiles to network devices (e.g. designated networkservers/routers for a serving area) using aggregate capacity analytics.

The depth first and breadth first approaches may be further explained byway of non-limiting example. Referring now to FIG. 2A, an exemplaryvisual representation of a network mapping is shown. The networkincludes on-ramp 260, nodes 261-269, and connections 270. In thisexample depth is defined as number of connections to on-ramp 260 for agiven path, Breadth is defined the number of peer nodes with aconnection to on-ramp 260 at the same depth. A depth first analysis fornode 266 yields multiple possible paths to on ramp 260. These includepath 261-262-266, path 261-263-264-262-266, and path261-263-264-267-266. Thus, node 266 has one path at depth 3 and twopaths at depth 5, Similarly nodes 264 and 265 each have paths at depth3. This process may continue until all paths for each node areidentified. Once the paths are identified, a breadth first approach maybe used to determine bandwidth balance load. Starting with node 261, thenodes are analyzed in order according to their shortest available path.Because all possible paths have been identified, the system may evaluateeach path involving a given node at a given depth in the path. Forexample, for the depth 2 evaluation of node 262 paths 261-262-264,261-262-265, and 261-262-266 are analyzed for telemetry optimization.Because all paths to nodes 265, 268, and 269 include at least path261-262-265, node 262 must have capacity equal to the aggregate of atleast those three nodes. If node 266 depends on its depth 3 path(261-262-266), this further adds to the capacity requirements of node262. Thus, a telemetry assignment may be made to prioritize use of path261-263-264-267-266 over use of path 261-262-266 for node 266. Thus, thefamilial load on 262 is reduced. This breadth first process may continueuntil all available paths at all depths are properly prioritized.Further, the depth and/or breadth first analyses may be periodicallyrepeated to ensure the telemetry prioritization is optimal for thecurrent net conditions. It will be appreciated that breadth and depthare relational terms and may be defined from any point in any network.The selection of on-ramp 260 is used to illuminate the principles ofeach of the approaches and is not meant to be limiting in nature.

The SRM may be used, inter alia, to build a mapping to supportapplications that require assessment or distribution of performancecharacteristics versus both time and system state. For example, aservice representative may used the SRM to quickly respond to a customercall for zero or degraded service using a visualization of the networkmapping to pin-point the locations within the network (e.g. EMN) whereservices are impaired or completely broken. Further, such visualizationsmay be implemented with select and zoom functions such that an operationmay focus on a specific potion of the network. In one implementation, a‘netmask’ view may be used. In such a view, the operator may select onlycertain portions of the network to be included in the visualization.Alternatively, all portions may be visualized, but the selectednetmasked portions may be highlighted (e.g. unblurred, enlarged,increased-contrast, special color, animated, etc.). The netmask portionsmay be selected by a specific network feature commonly shared by theincluded elements (e.g. network throughput, portion of IP-address,performance characteristics, peer-level, number of connections, numberof parent/child nodes, etc.).

Methods—

Referring now to FIG. 3, a flowchart illustrating one embodiment of ageneralized method 300 of service level management on an EMN is shown.At step 302 of the method 300, the SRM receives connectivity informationfrom the EMN. The connectivity information may include e.g., data on thenodes of the EMN and their corresponding interconnections. This data maybe collected passively by the SRM. For example, the SRM may monitorlocal network traffic (e.g. the SRM may view routing information onpackets routed between nodes, similar to the operation of a packetsniffing routine.). Further, the nodes themselves may send mapping datato the SRM. For example, the nodes may perform trace-route operation (orother route determining operation) on the received service to determinehow it is delivered to them. In this case, the trace-route data may thenbe sent to the SRM. Alternatively, the information may be actively fedto the SRM by one or more processes setup via a network administrator.Combinations of the foregoing (and yet other techniques) may also beutilized consistent with the methodology 300.

At step 304, the SRM generates a mapping of the EMN. The mappingincludes the various nodes of the EMN and routes between them. Invarious implementations, the mapping is used to make routing decisionsfor service delivery. For example, the SPN may select a point of entryfor the EMN based on the mapping. In networks with multiple “on-ramps”to the Internet, the choice of entry point may be used to ensure theoptimal route to the end destination for the service. The mapping mayalso be used to identify bottlenecks in the network. For example, if thenetwork has only one on/off ramp to the Internet, that ramp may limitthe number of users that may receive outside provision of differingcontent simultaneously.

At step 306 of the method 300, the SRM collects data related to theconnection performance of the interconnects among the nodes. This datamay comprise e.g., information on the connection technology between eachnode. Further, in some embodiments, the connection performance data mayinclude connection transmission history. For example, throughput andlatency for various activities may be monitored and recorded in thehistorical data. In addition, this data may also include networkspecific management data from the administrator of the network (e.g.data on bandwidth allowances, caps, throttling, etc.).

At step 308, the SRM generates one or more rules or other operationalconstraints based on the mapping of the performance data. The rules ofthe exemplary implementation guide delivery for how the SPN deliverscontent to the network, and how the nodes pass content to one another(e.g. parent nodes passing content to children, or peering, etc.).

For an exemplary IPTV embodiment, the rules may specify a video qualitylevel to be delivered to a node. The rules may specify withoutlimitation, options available, a default quality, or a maximum quality.Further, the rules may specify edge positioning for content. Forexample, some content may have varying quality or availability rules ifpre-positioned on a parent node.

Similarly, rules may vary for peer-to-peer connections. These rules maybe particularly flexible if the pre-positioning of the content placesthe content past one or more bottlenecks of the EMN identified in themapping of step 304.

In various implementations, the rules may also include tolerances forone or more performance options. In the IPTV example, this correspondsto, inter alia, a network activity level (or activity levels for parentnode or single node) at which certain quality options become unavailableor quality is preemptively reduced to avoid potential service failures.

It will also be appreciated that an administrator of the EMN (which maybe a human, or a supervisory process such as a computer program or otherartificial intelligence) may wish to prioritize certain other trafficover that of the service offered by the SPN. This comparativedeprioritization may reduce the end user experience (e.g., clarity,continuity or “smoothness” of streaming, video or audio quality,download or upload speed, etc.) of the users of the service of the SPN.Consequently, the rules of the SRM may be crafted to maximize userexperience, while complying with the prioritization prerogatives of theEMN administrator.

At step 310, the SRM provides the rules to the various servers and nodesinvolved in delivery of the service of the SPN. The SRM maintains anupdated database of rules for each of the elements. In variousimplementations, a network element (e.g. servers, parent nodes, nodes,etc.) involved in delivery queries the SRM for rules at the time ofdelivery. In other implementations, the SRM provides rule updates to theelements as they are generated. In yet other implementations ruleupdates may be delivered at regular intervals (e.g. once a minute, hour,day, week, etc.)

Referring now to FIG. 4, a flowchart illustrating one embodiment of ageneralized method 400 of service delivery on an EMN is shown. At step402, a node (or other element in the delivery chain) receives one ormore rules from the SRM. As discussed above, the frequency and theprocess of rule delivery may vary with the implementation.

At step 404, from the rules, the node identifies a route over which todeliver the service. In some embodiments, the rules may allow forvariance in the route based on network conditions (e.g. to route arounda high-activity bottleneck or a malfunctioning node, etc.). In otherembodiments, the route is fixed until an update to the rules is receivedfrom the SRM.

At step 406, the node determines a service level based on the rules androute. The service level is in the exemplary implementation selected tobe compatible with the rules for each of the nodes on the delivery path.For example, an end node may receive a service level lower than themaximum it is capable of handling, if the route involves a parent nodefor which the rules preclude such service levels. However, the end nodemay receive the higher level service if the parent node is not involvedin the route (e.g. in a peering connection, or other alternate path). Inan exemplary IPTV embodiment, an end user node may be limited to amoderate video quality from sources outside of the EMN, but may be ableto receive high quality video as long as the source is internal to theEMN.

At step 408, the node initiates delivery of the service in accordancewith the determined route and service level. To accomplish delivery thenode establishes any necessary links. For example in the case of peeringconnection, the node sets up a peer-to-peer link with the target nodefor service delivery. For IPTV embodiments, the node may setup one ormore video streams for delivery of the video to the end node.

Exemplary SRM Apparatus—

As noted above, the exemplary SRM entity 202 of the disclosure may takeon any number of different forms, include a server apparatus disposed onthe EMN. Referring now to FIG. 5, one exemplary SRM server apparatus 502configuration is shown. The server apparatus in this configurationincludes processing logic 504 (e.g., processor) running a number ofapplications, a memory bank 506 to support application execution, massstorage 508, and one or more interfaces to support connections to theEMN and various peripherals. The SRM in this embodiment is configuredfor implementation of the methods 300 and 400, discussed supra.

In an exemplary embodiment, the processing logic 504 and memory 506 arespecifically configured to support the applications running on theprocessing logic. Thus, the processing logic is connected via highbandwidth channels to each of the memory, mass storage, and anyincoming/outgoing interfaces.

The mass storage device is configured to store raw network data 510collected from the EMN. The raw network data is used to generate mappingdata 512, which is also stored on the mass storage device. The mappingdata may be retrieved, inter alia, for generation of server or noderules for service delivery or transmission to various ones of theservers and nodes for local use thereon. The mass storage device isfurther configured to store the server/node rules thereon. The servernode rules are in the exemplary embodiment made available fortransmission to and/or reference by the various entities of the network.For example, a node on a delivery route may require rules for its targetdelivery node. In this case, the node on the delivery route may querythe SRM, which then accesses the corresponding rule on its mass storagedevice. It will also be appreciated that the SRM may also access therules on the storage device, and “push” them to the delivery node in theabsence of a query.

The exemplary processing logic 504 maintains a number of applicationsrunning thereon. The EMN data collection application 516 collects rawnetwork connection information, layout information, performanceinformation, and/or routing information, which is stored as raw networkdata 510 on the mass storage device. In some variants, the SRM gathersthe raw network data by querying the various nodes on the network fortheir networking data (e.g. routing information, historical performancedata, etc.). In other variants, the raw network data may be provided bya network administrator or other entity tasked with collection anddissemination of this data. It will be appreciated that such networkadministrator or other entity may be configured such that, at least incertain circumstances, it may not provide exact or empirical values forthe raw data, but rather may provide estimates, projections, or othertypes of “derivative” or speculative data. Alternatively, theadministrator may provide raw data based on network policies (ratherthan network capability-limited values), and/or estimates based onhistorical performance. In yet another variant, the data from thevarious nodes may be “pushed” to the SRM in the absence of a querytherefrom, such as according to a periodic schedule, occurrence of anevent (e.g., when sufficient bandwidth exists, when a change in networkconfiguration occurs, etc.).

In the exemplary implementation, the raw network data 510 is organizedinto the mapping data 512 by the EMN mapping application 518. The rawnetwork data may be used by the EMN mapping application to piecetogether that layout of the network, and to determine reasonableperformance estimates for the various nodes on the network (depending onthe service in question and the route used). The mapping data may alsobe available as a visualization. The visualization may be generated bythe SRM or the mapping data 512 may be transmitted to another system fordisplay as a visualization. As discussed above, such visualizations maybe used to, inter alia, assist in the diagnoses of networkissues/failures.

The mapping data 512 is then used by the rules generation application522 to generate rules for service delivery. In various embodiments, therules a generated to offer the optimal telemetry layout of the servicedelivered. In an exemplary implementation, the mapping data may be usedto provide a historical mapping of traffic patterns related to thedelivered services (and general network traffic). Thus, administrators(e.g. the EMN administrator or a service provider representative) mayapply general traffic management polices at the SRM level while takingadvantage of the information available at the SRM. The policies are thenalso considered in rule generation.

The rules distribution application 524 running on the processing logic504 then distributes the rules to the nodes of the EMN and any serversinvolved in service delivery. As discussed with respect to the exemplarymethod 400 above, the timing of the delivery is dependent upon theimplementation. Thus, the rules distribution engine may be configured todeliver the rules, without limitation, periodically, upon request, asgenerated, and/or in response to a service request.

The exemplary interface 512 comprises any number of high-speed dataconnections to facilitate the inclusion of the SRM server in the networkand the execution of the SRM's activities. The connections must supplybandwidth sufficient to support the incoming raw data, service requests,and outgoing rules, and include any of the interfaces necessary tosupport any of the network architectures discussed above. Suchconnections or interfaces may include for instance Gigabit Ethernet/10G,1EEE-1394, Thunderbolt™, optical networking, and/or other well knownnetworking technologies. Further, the interfaces may allow connection adisplay for a presentation of a visualization of the EMN mapping.

In other variants, the SRM server may be implemented one or moresoftware routines on a network server providing other functions on theEMN.

It will also be appreciated that the functions of the SRM may bedistributed over multiple network entities including, withoutlimitation, one or more of the nodes discussed herein.

In yet other implementations, the SRM may be disposed off of the EMN(e.g. on an Internet connected server, or an entity on the SPN (headend,etc.), or a cloud computing entity). In one variant, one or moreroutines running the nodes of the EMN forward raw data from the EMN tothe remote SRM. In others variants, the SRM receives the raw data fromthe EMN from a single source, such as an administration node.

It will also be appreciated that in some embodiments, the SRM may bepartially disposed on the EMN and partially disposed on other networks(e.g. on an Internet server, or on the SPN, etc.). For example, the EMNdata collection application may run on a node within the EMN, and theapplication may pass the raw data to a server on the SPN running the EMNmapping application, the rules generation application, and the rulesdistribution application.

Exemplary Operation—

Referring now to FIG. 6, an exemplary embodiment of a visualization of anetwork mapping is shown. In this mapping, the EMN 602 (behind thefirewall 604) is divided into three subnets (610, 612, 614) each withparent nodes (620, 622, 632, and 624) and end user nodes (618) allmanaged by an internet protocol SRM (IP-SRM) 606. The EMN utilizes itsown IP address space beyond the firewall.

The administrator of the network has specific polices for each of thetwo wired subnets (610 and 612). The third subnet 614 (wireless) has noassociated policy limitations; thus, rules may be made freely via theIP-SRM to optimize service delivery from the SPN server 608 to avoidservice failures (e.g., total video loss). In this case, the service inquestion is an IPTV delivery system.

The first wired subnet 610 is denoted with a subnet mask of e.g.,10.xxx.xxx.xxx. This subnet comprises the general use wired subnet ofthe institution. The EMN administrator has setup a specific policy thatthe maximum video bitrate for the wired subnet 610 is 3.5 Mbit/sregardless of system performance. All video delivered to the wiredsubnet 610 must pass though parent node 620.

The second wired subnet 612 is denoted with an exemplary subnet mask of172.168.xxx.xxx. This subnet is the executive wired subnet. The EMNadministrator policy designates a default video bitrate of 8 Mbit/s forthis subnet. Further, the administrator has issued a directive that aperformance related video downgrade below 5 Mbit/s for a user of thissubnet should be treated as a service failure (i.e., a service alertshould be generated, problem node(s) should be identified, servicereroutes should be performed). However, if rerouting cannot solve theissue, video at a lower bitrate is still to be delivered if possible toavoid actual service failure. All video delivered to the executivesubnet 612 must pass through parent node 622 or parent node 632.

The wireless subnet 614 is denoted with a subnet mask of192.168.xxx.xxx. No policy limits are placed on the wireless network.All video delivered must pass through parent node 624.

Parent nodes 620, 622, 632, and 624 each have multiple high-throughputexternal connections to the internet.

Initially, 100 users utilize the IPTV service on the wireless subnet614, in this case, requiring 15 unique streams (peering accounts for allothers); system delivers video at 8 Mbit/s. Roughly 5,000 users utilizethe service on the wired subnet 610; 450 unique streams are delivered at3.5 Mbit/s (i.e. bitrate limited by the IP-SRM). Usage for the wiredsubnet 610 remains steady. For the executive network 612, current usagelevels are at 1,100 users representing 120 unique streams all deliveredat 8 Mbit/s.

At primetime (a high-usage period sometime later), wireless subnet usagegrows to 1,000 users requesting 90 unique streams, the IP-SRM 606reduces the video quality of 82 of the 90 streams to 750 Kbit/s; theremaining eight streams are delivered at 3.5 Mbit/s. The eighthigher-bandwidth streams represent those that account for the greatestproportion of the peering (eight streams serving ˜600 users viapeering). The wired subnet 610 usage grows to 10,000 users and 670streams; however delivery remains steady at 3.5 Mbit/s. Usage of theexecutive subnet 612 remains steady, but parent node 632 is overwhelmedwith prioritized above that of the IPTV traffic, and the IP-SRM reducesthe delivery quality to 3.5 Mbit/s temporarily for 400 users of theexecutive network. The IP-SRM reroutes their corresponding streamsthrough the parent node 622 and restores their video bitrate to 8Mbit/s. The IP-SRM generates a report for this SPN operator and the EMNadministrator identifying parent node 632 as having an acute performanceissue.

It will be recognized that while certain aspects are described in termsof a specific sequence of steps of a method, these descriptions are onlyillustrative of the broader methods of the disclosure, and may bemodified as required by the particular application. Certain steps may berendered unnecessary or optional under certain circumstances.Additionally, certain steps or functionality may be added to thedisclosed embodiments, or the order of performance of two or more stepspermuted. All such variations are considered to be disclosed and claimedherein.

While the above detailed description has shown, described, and pointedout novel features of the invention as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the invention. Theforegoing description is of the best mode presently contemplated ofcarrying out the techniques and architectures disclosed herein. Thisdescription is in no way meant to be limiting, but rather should betaken as illustrative of the general principles of the disclosure. Thescope of the invention should be determined with reference to theclaims.

1.-23. (canceled)
 24. A computerized method of managing service levelson a digital data network, the computerized method comprising:receiving, at a computerized centralized resource management entity ofthe digital data network, networking data associated with a plurality ofnetwork nodes of the digital data network; based at least in part on thenetworking data, determining a layout of the digital data deliverynetwork, the layout of the digital data network comprising at least afirst subnet and a second subnet; receiving, at the computerizedcentralized resource management entity, performance data for at least afirst node and a second node of the plurality of nodes, the first nodeof the plurality of nodes belonging to the first subnet and the secondnode of the plurality of nodes belonging to the second subnet;determining, based at least in part on the layout and the performancedata, one or more delivery rules for the first node of the plurality ofnodes; causing, via at least the computerized centralized resourcemanagement entity, delivery of digitally rendered content to the firstnode of the first subnet, the delivery in compliance with the one ormore delivery rules; receiving, at the computerized centralized resourcemanagement entity and from a computerized process of the network, dataindicative of one or more policies; and enforcing, via at least thecomputerized centralized resource management entity, at least one of theone or more policies at the second node, the at least one of the one ormore policies specifying a maximum video bitrate for the second noderegardless of the performance data.
 25. The computerized method of claim24, further comprising optimizing, using at least the computerizedcentralized resource management entity and a service provider network(SPN) server, service delivery within the first subnet, the first subnetcomprising a wireless subnet with no policy limitations; and wherein thereceiving of the data indicative of the one or more policies from thecomputerized process of the network obviates a need for the computerizedof the network to update policies at the second node of the at least onenode of the plurality of nodes based on one or more settings altered bythe computerized centralized resource management entity.
 26. Thecomputerized method of claim 24, wherein the causing the delivery ofdigitally rendered content in compliance with the one or more deliveryrules comprises reducing a bitrate quality of a first portion of aplurality of data streams in the first subnet during a certain period oftime, and maintaining the bitrate quality of a second remaining portionof the plurality of data streams, the second remaining portion of theplurality of streams utilizing a plurality of peer-to-peer connectionsthereby serving a greater proportion of user devices relative to thefirst portion of the plurality of data streams.
 27. The computerizedmethod of claim 24, further comprising: utilizing the determined layoutof the digital data network to generate a visualization of the digitaldata network; and selecting a portion of the digital data networkrepresented on the visualization, the selecting (i) based at least on apeer-level with the network and (ii) enabling identification of one ormore locations of the digital data network that are impaired.
 28. Thecomputerized method of claim 24, further comprising: utilizing thedetermined layout of the digital data network to generate avisualization of the digital data network; and selecting a portion ofthe digital data network represented on the visualization based at leaston one or more performance analytic data elements, the one or moreperformance analytic data elements comprising an indication of totaldata throughput for at least one node of the plurality of nodes.
 29. Thecomputerized method of claim 24, further comprising: receiving, at thecomputerized centralized resource management entity, performance datafor a third node of the plurality of nodes, the third node of theplurality of nodes belonging to a third subnet of the digital datanetwork; based at least on the received performance data for the thirdnode, identifying one or more transmission issues at the third node; andvarying, based at least on the identifying, at least a portion of a datadelivery route for the third subnet.
 30. The computerized method ofclaim 24, wherein the digital data network comprises an externallymanaged network associated with one or more of: (i) a university, (ii) acommercial enterprise, and (iii) a government entity.
 31. Thecomputerized method of claim 24, further comprising: determining, basedat least in part on the layout of the digital data network, a pluralityof respective telemetry profiles for the plurality of network nodes; andpre-assigning the plurality of respective telemetry profiles to one ormore of the plurality of network nodes using aggregate capacityanalytics; and wherein the plurality of respective assigned telemetryprofiles are configured to designate prioritized routing for servedareas corresponding to the one or more of the plurality of networknodes.
 32. A computerized method of digital content delivery on adigital data network, the computerized method comprising: receiving, ata computerized resource management entity of the digital network, firstdata associated with a mapping of the digital data network, the firstdata comprising (i) system performance data and (ii) data relating to aplurality of subnets of the digital data network; for a first subnet ofthe plurality of subnets, the first subnet comprising a first pluralityof infrastructure elements: based at least in part on the received firstdata, identifying a route for delivery of digitally rendered content toat least one computerized network device; receiving second dataindicative of at least one connection profile associated with one ormore of the first plurality of infrastructure elements and the at leastone computerized network device; identifying one or more of theplurality of infrastructure elements associated with congestion, theidentifying based at least in part on the second data; based at least inpart on the second data and the identified route, identifying a firstquality level for the delivery of the digitally rendered content; andcausing transmission of the digitally rendered content in accordancewith the first quality level, the causing of the transmission of thedigitally rendered content comprising causing pre-positioning of thedigitally rendered content at a particular one of the first plurality ofinfrastructure elements disposed further downstream on the route thanthe identified one or more of the plurality of infrastructure elementsassociated with the congestion; and for a second subnet of the pluralityof subnets: causing a transmission of the digitally rendered content inaccordance with a predetermined second quality level, the pre-determinedsecond quality level set by a computerized management entity of thedigital data network and irrespective of the system performance data.33. The computerized method of claim 32, further comprising, for a thirdsubnet of the plurality of subnets, the third subnet comprising a thirdplurality of infrastructure elements: based at least in part on anetwork layout, assigning at least one delivery rule to at least one ofthe third plurality of infrastructure elements; wherein the at least onedelivery rule is configured to cause a reduction in a third qualitylevel for a first portion of a plurality of data streams of the thirdsubnet during a prescribed period of time, and maintain the thirdquality level for a second remaining portion of the plurality ofstreams, wherein the second remaining portion of the plurality of datastreams serves a greater proportion of users relative to the firstportion of the plurality of data streams via at least a plurality ofpeer-to-peer connections.
 34. The computerized method of claim 32,wherein the causing of the transmission of the digitally renderedcontent in accordance with the pre-determined second quality levelcomprises initiating a transmission of the digitally rendered content inaccordance with a pre-determined bitrate of an Internet Protocoltelevision (IPTV) service.
 35. The computerized method of claim 32,further comprising generating visualization data based on the receivedfirst data, the generating of the visualization data comprisingconfiguring selecting and zooming functions configured to display one ormore specific portions of the mapping of the digital data network, theselecting and zooming functions enabling identification of one or moreimpairments of the one or more specific portions of the mapping. 36.Computer readable apparatus comprising a non-transitory storage medium,the non-transitory medium comprising at least one computer programhaving a plurality of instructions, the plurality of instructionsconfigured to, when executed on a processing apparatus: collect, at acomputerized network management entity, raw networking data relating toa plurality of network nodes; analyze at least the collected rawnetworking data to determine a network layout; analyze at least thecollected raw networking data to associate one or more performancelevels with at least one of the plurality network nodes; and based atleast in part on the determined network layout and the one or moreperformance levels, assign at least one delivery rule to the at leastone of the plurality of network nodes, the at least one of the pluralityof network nodes belonging to a first subnet of a network; wherein theat least one delivery rule is configured to cause a reduction in a videoquality level for a first portion of a plurality of data streams of thefirst subnet during at least a first period of time, and maintain anextant video quality level for a second portion of the plurality of datastreams, wherein the second portion of the plurality of data streamsserves a greater proportion of user devices relative to the firstportion of the plurality of data streams.
 37. The computer readableapparatus of claim 36, wherein the video quality level comprises abitrate associated with an Internet Protocol television (IPTV) service.38. The computer readable apparatus of claim 36, wherein individualnodes of the plurality of network nodes of the first subnet each utilizea first common content source.
 39. The computer readable apparatus ofclaim 38, wherein the first common content source comprises at least oneUniform Resource Locator (URL) provided by the computerized networkmanagement entity.
 40. The computer readable apparatus of claim 39,wherein the plurality of network nodes comprise one or more nodesbelonging to a second subnet, each of the one or more nodes belonging tothe second subnet having a second common content source, the secondcommon content source different than the first common content source ofthe individual nodes of the first subnet.
 41. The computer readableapparatus of claim 38, wherein: the plurality of network nodes compriseone or more nodes belonging to a second subnet; and the plurality ofinstructions are further configured to, when executed on the processingapparatus, enforce, via at least the computerized network managemententity, one or more policies at the one or more nodes belonging to thesecond subnet, the one or more policies specifying a quality level forthe one or more nodes, the quality level determined irrespective of thecollected raw networking data.
 42. The computer readable apparatus ofclaim 41, wherein: the plurality of network nodes comprise one or morenodes belonging to a third subnet; and the plurality of instructions arefurther configured to, when executed on the processing apparatus, reducea video quality level of digital content delivery from the one or morenodes belonging to the third subnet until a congestion level falls belowa determined threshold, the video quality level comprising a bitrate forthe digital content delivery.